advanced DXL layout

Hi guys,

 

Maybe someone can help me.

 

This is the challenge (see picture below):

- I have two modules: in the one there is a lot of text and dummies (out-links). In another module there is for every dummy a certain value & unit (in-links).

- For the first module there shall be an additional column (-->Layout DXL?) and the objects must not be changed.

- The content of the column should be the object text from module 1 where the dummies are replace (value and unit from the other module) .

 

Any kind of help or hints is more than welcome. I hope it is clear what I mean.

 

Thank you already in advance for the help!

 

Best regards from Europe,

Rafael

 


gercompany - Mon May 15 11:46:12 EDT 2017

Re: advanced DXL layout
Mathias Mamsch - Thu May 18 17:05:43 EDT 2017

In the end it is not that complicated todo in DXL. All you need to know is how to navigate beween the object and how to navigate links from DXL. This has all been discussed overwhelmingly often in the forum, so all the information is there and you can find it by the search function (or come back to this thread if you struggle with specific problems).

What is not clear from your description is, if you use actual links or only text "keys" that reference to your other module? Or both?

Are you using this modue setup, so you can reference the same information from multiple modules? I saw a lot of those setups during my time as RM consultant and found that there are two ways to handle that situation: a) you can split your whole module contents apart to keep shared information in one central place b) you can duplicate the information and have to deal with the synchronization later. I found way b) to be MUCH more intuitive for most people, as this is as you work in other systems too. If you split your modules you create many many problems with important things like readability, exports, baselining, etc. Most of the times it is also not possible to split the information in a way that fits the process.

That was one reason that we implemented BranchManager for DOORS which is a generic Branch/Merge solution for DOORS allowing you to share information between multiple modules but still keep baselining, readability, etc. easy and the lifecycle of the different projects decoupled. Before you start introducing DXL scripts to solve the problem that you introduced yourself by splitting the modules apart, think thoroughly about the other problems that come with a setup like this.

Regards, Mathias